Adaptive self-optimizing network using closed-loop feedback

ABSTRACT

Systems, methods, and apparatus for an adaptive self-optimizing network using closed-loop feedback are disclosed. A method for sharing network resources comprises receiving, by a network operations center (NOC), access requests for users subscribed to an external network. The method further comprises receiving, by the NOC, a summary of key performance indicators from at least one internal network. Also, the method comprises determining, by the NOC, whether at least one internal network has available resources by analyzing the summary of key performance indicators and user demand from the access requests. Further, the method comprises allowing, by the NOC when the NOC determines that there are available resources, at least some of the users from the external network to connect to at least one internal network according to the available resources.

CROSS-REFERENCE TO RELATED APPLICATION

This application is related to U.S. patent application Ser. No.16/228,627, filed on Dec. 20, 2018, the entire disclosure of which isexpressly incorporated by reference herein.

FIELD

The present disclosure relates to networks, such as mobile wireless(e.g., cellular, satellite, tactical military, etc.) networks. Inparticular, the present disclosure relates to adaptive self-optimizingnetworks using closed-loop feedback.

BACKGROUND

Currently, configurations (e.g., payload configurations) of mobilenetworks are changed manually according to changing user demand fornetwork resources (e.g., loading patterns), ambient environmentalconditions, and/or system performance (e.g., including failures). Inparticular, a network access node's configuration is changed by anetwork operations center (NOC) manually generating and sending payloadconfiguration command signals to the access node. This conventionallyused, manual procedure is very tedious and time consuming for thenetwork operator. In addition, since this conventional procedure ismanually-driven and does not incorporate closed-loop feedback, there isno self-organization and self-optimization capability that would allowthe network to dynamically change its configuration to adapt to changinguser locations and loading patterns.

In light of the foregoing, there is a need for an improved technologyfor adapting configurations to adapt the network to changes in usermobility and capacity demands.

SUMMARY

The present disclosure relates to a method, system, and apparatus for anadaptive self-optimizing network using closed-loop feedback. In one ormore embodiments, a method for an adaptive network of network accessnodes comprises receiving, by a global network operations center (GNOC),operator inputs. The method further comprises generating, by the GNOC, aglobal policy according to the operator inputs. Also, the methodcomprises generating, by the GNOC and/or a distributed network gateway(GW), configuration commands for configurations for at least one of thenetwork access nodes based on the global policy. In addition, the methodcomprises transmitting, by the GNOC and/or the distributed network GW,the configuration commands to at least one of the network access nodes.Additionally, the method comprises transmitting, by the distributednetwork GW, a summary of key performance indicators to the GNOC. Also,the method comprises revising, by the GNOC, the global policy accordingto the summary of key performance indicators. Further, the methodcomprises repeating steps of the method above that follow the generatingof the global policy by the GNOC.

In one or more embodiments, the method further comprises generating, bya regional network operations center (RNOC), a regional policy. In atleast one embodiment, the method further comprises revising, by theGNOC, the global policy according to the regional policy. In someembodiments, the regional policy comprises admission control, mobilitymanagement, channel allocations, carrier allocations, bearerallocations, power management, and/or forward and/or return (FWD/RTN)scheduling policies. In one or more embodiments, the RNOC is locatedwithin a distributed network gateway (GW).

In at least one embodiment, the GNOC is located within a distributednetwork gateway (GW). In some embodiments, the global policy comprisesbeam allocations, capacity allocations, software-defined network (SDN)management, and/or admission control policy. In one or more embodiments,the operator inputs comprise frequency spectrum planning, trafficplanning, and/or contingency plans. In some embodiments, the keyperformance indicators comprise subscriber demand, MODEM power profiles,beam and carrier (beam/carrier) utilization, session blocking rates,random access channel (RACH) success rates, bearer success rates,session setup latency statistics, and/or handover success rates.

In one or more embodiments, the network access nodes are space vehicles,high-altitude platforms, airborne vehicles, terrestrial vehicles, marinevehicles, or fixed terrestrial cellular or wireless base stations. In atleast one embodiment, the space vehicles are satellites. In someembodiments, the satellites comprise a geosynchronous earth orbit (GEO)satellite constellation, a low earth orbit (LEO) satelliteconstellation, a medium earth orbit (MEO) satellite constellation, asupersynchronous GEO satellite constellation, or a hybrid satelliteconstellation comprising one or more constellations or constellationtypes.

In at least one embodiment, the method further comprises generating, bythe GNOC and/or the distributed network GW, extensible markup language(XML) models for the configurations for at least one of the networkaccess nodes according to the global policy. In some embodiments, themethod further comprises generating, by the GNOC and/or the distributednetwork GW, the configuration commands according to the XML models.

In one or more embodiments, the method further comprises transmitting,by at least one of the network access nodes, telemetry to the GNOCand/or the distributed network GW.

In at least one embodiment, a system for an adaptive network of networkaccess nodes comprises a global network operations center (GNOC)configured to receive operator inputs, to generate a global policyaccording to the operator inputs, to generate configuration commands forconfigurations for at least one of the network access nodes based on theglobal policy, and to revise the global policy according to a summary ofkey performance indicators. The system further comprises a distributednetwork gateway (GW) configured to transmit the summary of keyperformance indicators to the GNOC. In one or more embodiments, thedistributed network gateway (GW) and/or the GNOC are further configuredto transmit the configuration commands to at least one of the networkaccess nodes.

In one or more embodiments, the system further comprises a regionalnetwork operations center (RNOC) configured to generate a regionalpolicy. In some embodiments, the GNOC is further configured to revisethe global policy according to the regional policy.

In at least one embodiment, a method for configuring a configuration fora network access node comprises generating XML models for theconfiguration for the network access node. The method further comprisesgenerating configuration commands for the network access node accordingto the XML models. Further, the method comprises configuring theconfiguration for the network access node according to the configurationcommands. In some embodiments, the XML models are generated according toa global policy.

In one or more embodiments, a method for sharing network resourcescomprises receiving, by a network operations center (NOC), accessrequests for users subscribed to an external network. The method furthercomprises receiving, by the NOC, a summary of key performance indicatorsfrom at least one internal network. Also, the method comprisesdetermining, by the NOC, whether at least one internal network hasavailable resources by analyzing the summary of key performanceindicators and user demand from the access requests. Further, the methodcomprises allowing, by the NOC when the NOC determines that there areavailable resources, at least some of the users from the externalnetwork to connect to at least one internal network according to theavailable resources.

In at least one embodiment, the method further comprises connecting atleast some of the users from the external network to at least oneinternal network via at least one user-to-network interface (UNI). Insome embodiments, the external network is connected to the at least oneinternal network via at least one external network-to-network interface(ENNI). In one or more embodiments, the NOC controls operations of theat least one internal network. In at least one embodiment, when thereare more than one of the internal networks, the internal networks areconnected to each other via at least one internal network-to-networkinterface (INNI). In some embodiments, users from at least one internalnetwork are connected to the at least one internal network via at leastone user-to-network interface (UNI).

In one or more embodiments, the external network and at least oneinternal network each comprise a vehicle, a router, a network operatingsystem (NOS), an open virtual switch (OVS), a backbone edge bridge(BEB), a backbone core bridge (BCB), a virtual network function (VNF),and/or provider backbone bridging-traffic engineering (PBB-TE). In atleast one embodiment, the network access node is a space vehicle, ahigh-altitude platform, an airborne vehicle, a terrestrial vehicle, amarine vehicle, or a fixed terrestrial cellular or wireless basestation. In some embodiments, the space vehicle is a satellite, and thesatellite is a geosynchronous earth orbit (GEO) satellite, a low earthorbit (LEO) satellite, a medium earth orbit (MEO) satellite, or asupersynchronous GEO satellite.

In at least one embodiment, a software defined network (SDN) controllerof the NOC controls connections of at least one externalnetwork-to-network interface (ENNI), at least one internalnetwork-to-network interface (INNI), and at least one user-to-networkinterface (UNI).

In one or more embodiments, a system for sharing network resourcescomprises an external network, and at least one internal network. Thesystem further comprises a network operations center (NOC) configured toreceive access requests for users subscribed to an external network, toreceive a summary of key performance indicators from at least oneinternal network, to determine whether at least one internal network hasavailable resources by analyzing the summary of key performanceindicators and user demand from the access requests, and to allow, whenthe NOC determines that there are available resources, at least some ofthe users from the external network to connect to at least one internalnetwork according to the available resources.

In at least one embodiment, at least some of the users from the externalnetwork are connected to at least one internal network via at least oneuser-to-network interface (UNI). In one or more embodiments, the NOC isconfigured to control operations of the at least one internal network.In one or more embodiments, a software-defined network (SDN) controllerof the NOC is configured to control connections of at least one externalnetwork-to-network interface (ENNI), at least one internalnetwork-to-network interface (INNI), and at least one user-to-networkinterface (UNI).

The features, functions, and advantages can be achieved independently invarious embodiments of the present disclosure or may be combined in yetother embodiments.

DRAWINGS

These and other features, aspects, and advantages of the presentdisclosure will become better understood with regard to the followingdescription, appended claims, and accompanying drawings where:

FIG. 1 is a block diagram showing the management architecture for thedisclosed system for an adaptive self-optimizing network usingclosed-loop feedback, in accordance with at least one embodiment of thepresent disclosure.

FIG. 2 is a block diagram showing the distributed functionalarchitecture for the disclosed system for an adaptive self-optimizingnetwork using closed-loop feedback, in accordance with at least oneembodiment of the present disclosure.

FIGS. 3A and 3B together form a flow chart showing the method foroperation of the disclosed system for an adaptive self-optimizingnetwork using closed-loop feedback relating to FIG. 1, in accordancewith at least one embodiment of the present disclosure.

FIG. 4 is a diagram showing the top level architecture for the disclosedsystem for an adaptive self-optimizing network using closed-loopfeedback, in accordance with at least one embodiment of the presentdisclosure.

FIG. 5 is a diagram showing further details of the operations manager ofFIG. 4, in accordance with at least one embodiment of the presentdisclosure.

FIG. 6 is a flow chart showing the method for operation of the disclosedsystem for an adaptive self-optimizing network using closed-loopfeedback relating to FIG. 4, in accordance with at least one embodimentof the present disclosure.

FIG. 7 is a flow chart showing the method for configuring aconfiguration for a network access node relating to FIG. 5, inaccordance with at least one embodiment of the present disclosure.

DESCRIPTION

The methods and apparatus disclosed herein provide an operative systemfor an adaptive self-optimizing network using closed-loop feedback. Inone or more embodiments, the system of the present disclosure providesadaptive, closed-loop management of a network (e.g., a satellitenetwork) in a manner that allows for the network to dynamically adapt tochanging user demand for network resources (e.g., loading patterns),ambient environmental conditions, and/or system performance (e.g.,including failures). In particular, the disclosed system allows formanagement of network resources by using closed-loop feedback ofreal-time statistics pulled from the system.

Specifically, a distributed microservices-based architecture is employedby the system to disseminate a centralized policy (e.g., a globalpolicy) from a global network operations center (GNOC) to a collectionof gateways (GWs) (e.g., ground stations) located throughout the system.Additionally, the system employs a system resource manager (SRM) thatprovides essential functions for connection management, beam management,carrier management, admission control, routing management, signalingmanagement, and/or automated system configuration. The centralizedpolicy, which is disseminated to the gateways, is derived from keyperformance indicators (KPIs) pulled from various elements of the systemto create a closed-loop, adaptive feedback mechanism.

In addition, standards-based protocols and interfaces are employed forevolvability and interoperability of the network. Extensible markuplanguage (XML) based schemas developed to model the network accessnode's configuration (e.g., satellite payload configuration) areutilized by the system to allow the network access nodes (e.g.,satellites) residing in the network (e.g., constellation) to be managedseamlessly as part of the network via an operations manager. Theadaptive nature of the disclosed system allows for the network ofnetwork access nodes (e.g., satellite constellation) to behave as aself-organizing and self-optimizing network.

The system of the present disclosure has the following advantageousfeatures. Firstly, the system employs adaptive, closed-loop feedbackfrom the network to dynamically self-optimize performance. Secondly, thesystem provides tight integration of all of the essential functionsrequired for system resource management of a large nodal network (e.g.,satellite network). Thirdly, the system provides a reusable frameworkarchitecture that can be applied to a single satellite system, aconstellation of satellites (e.g., a geosynchronous earth orbit (GEO)satellite constellation, a low earth orbit (LEO) satelliteconstellation, a medium earth orbit (MEO) satellite constellation, or asupersynchronous GEO satellite constellation, with no inclination orwith inclination), or a hybrid satellite constellation comprisingmultiple different satellite constellations (e.g., a GEO and MEOsatellite constellation, a LEO and MEO satellite constellation, or a GEOand LEO satellite constellation). And, fourthly, the disclosed systemhas the ability to optimize system policy based on dynamic feedback andgenerate system configuration commands that can be automatically pushedthroughout the network in real time.

In the following description, numerous details are set forth in order toprovide a more thorough description of the system. It will be apparent,however, to one skilled in the art, that the disclosed system may bepracticed without these specific details. In the other instances, wellknown features have not been described in detail, so as not tounnecessarily obscure the system.

Embodiments of the present disclosure may be described herein in termsof functional and/or logical components and various processing steps. Itshould be appreciated that such components may be realized by any numberof hardware, software, and/or firmware components configured to performthe specified functions. For example, an embodiment of the presentdisclosure may employ various integrated circuit components (e.g.,memory elements, digital signal processing elements, logic elements,look-up tables, or the like), which may carry out a variety of functionsunder the control of one or more processors, microprocessors, or othercontrol devices. In addition, those skilled in the art will appreciatethat embodiments of the present disclosure may be practiced inconjunction with other components, and that the systems described hereinare merely example embodiments of the present disclosure.

For the sake of brevity, conventional techniques and components relatedto networks, and other functional aspects of the system (and theindividual operating components of the systems) may not be described indetail herein. Furthermore, the connecting lines shown in the variousfigures contained herein are intended to represent example functionalrelationships and/or physical couplings between the various elements. Itshould be noted that many alternative or additional functionalrelationships or physical connections may be present in one or moreembodiments of the present disclosure.

In various embodiments, the disclosed system for an adaptiveself-optimizing network using closed-loop feedback employs aconstellation of satellites. It should be noted that the disclosedsystem for an adaptive self-optimizing network using closed-loopfeedback may be employed for network access nodes (e.g., high-altitudeplatforms, airborne vehicles, terrestrial vehicles, marine vehicles,and/or fixed terrestrial base stations) other than satellites asdisclosed herein. The following discussion is thus directed tosatellites without loss of generality.

FIG. 1 is a block diagram 100 showing the management architecture forthe disclosed system for an adaptive self-optimizing network usingclosed-loop feedback, in accordance with at least one embodiment of thepresent disclosure. In this figure, a network access node constellation110 comprises a system of interconnected configurable network accessnodes 105. In one or more embodiments, the network access nodes 105 maybe space vehicles (e.g., satellites, high-altitude platforms (HAPs),such as balloons or high-endurance unmanned aerial vehicles (UAVs)),airborne vehicles (e.g., aircraft or unmanned aerial vehicle (UAVs)),terrestrial vehicles (trucks, tanks, or unmanned ground vehicles(UGVs)), marine vehicles (e.g., ships, submarines, or an unmannedunderwater vehicles (UUVs)), and/or fixed terrestrial based stations. Insome embodiments, when the network access node constellation 110 is aconstellation of satellites, the satellite constellation may be ageosynchronous earth orbit (GEO) satellite constellation (with noinclination or with inclination), a low earth orbit (LEO) satelliteconstellation (with no inclination or with inclination), a medium earthorbit (MEO) satellite constellation (with no inclination or withinclination), a supersynchronous GEO satellite constellation (with noinclination or with inclination), or a hybrid satellite constellationcomprising multiple different satellite constellations (e.g., a GEO andMEO satellite constellation, a LEO and MEO satellite constellation, or aGEO and LEO satellite constellation) (with no inclination or withinclination). It should be noted that when the network access nodes 105are satellites, the satellites will each have a configurable payload115.

Also in this figure, a global network operations center (GNOC) is shownto comprise an operation center (xOC) 125 (that is unique to the type ofnetwork the network access nodes use), a network operations center (NOC)130, and a cybersecurity operations center (CSOC) 135. The xOC 125, ifthe network access node 105 is a satellite, maintains the orbit of thesatellite, receives tracking and telemetry (e.g., regarding thesatellite's location, configuration, and state of health), transmitscommands (e.g., satellite bus and payload configuration commands, andmanages antenna pointing). The CSOC 135 manages the security of thesystem (e.g., by detecting, notifying of, and mitigating cyber attacks).The NOC 130 comprises a system resource manager (SRM) 140 that managesthe resources of the network of network access nodes.

Also in FIG. 1, at least one distributed network gateway (GW) 145 isshown. Each distributed network GW 145 is associated with at least onenetwork access node 105, and each network access node 105 is associatedwith at least one distributed network GW 145. Each distributed networkGW 145 is shown to comprise an SRM 150 for GW monitoring and control(M&C) 155. In addition, each distributed network GW 145 comprises anantenna farm (e.g., a plurality of transmit and receive antennas) 160,radio frequency equipment (RFE) and switching 165, MODEMs(modulator/demodulator) and optionally a ground-based beamforming (GBBF)network 170, and network architecture/infrastructure 175 (e.g.,switches, routers, firewalls, etc.). The GW M&C 155 performs monitoringand control of the state of health of the antennas and RFE, networkinfrastructure, and/or control of the feederlink antennas of the antennafarm. Each distributed network GW 145 is in communication (via fiber(wire) and/or wirelessly (via satellite)) with the GNOC 120 and may alsobe in communication (via fiber (wire) and/or wirelessly (via satellite,e.g., by feeder-link)) with its collection of attached network accessnodes 105.

In addition, the disclosed system may comprise a regional NOC (RNOC)180, as is shown in FIG. 1. The RNOC 180 comprises a SRM 185. The RNOC180 is in communication (via fiber (wire) and/or wirelessly (viasatellite)) with the GNOC 120 and/or is in communication (via fiber(wire) and/or wirelessly (via satellite)) with at least one distributednetwork GW 145.

The GNOC 120 and RNOC 180 may each be co-located with (or within) adistributed network GW. As such, the GNOC 120 and the RNOC 180 may alsocomprise the same units (e.g., antenna farm 160, RFE and switching 165,MODEMs and optional GBBF 170, and network infrastructure 175) as adistributed network GW 145 as depicted in FIG. 1. As such, the SRM 140of the GNOC 120 and the SRM 150 of the RNOC may perform GW M&C 155 bymonitoring and control of the state of health of the antennas and RFE,network infrastructure, and/or control of the feederlink antennas of theantenna farm.

During operation of the disclosed system, the SRM 140 of the GNOC 120receives operator inputs 190 from operators (e.g., refer to 410 of FIG.4). The operator inputs 190 may comprise frequency spectrum planning,traffic planning, and/or contingency plans. The SRM 140 of the GNOC 120generates a (initial) global policy 191 according to the parameters ofthe operating inputs 190. The global policy 191 may comprise beamallocations (e.g., the size, shape, location, and power of the antennabeams), capacity allocations (e.g., the location of terminals (users)and user demands), software-defined network (SDN) management (e.g., therouting and signaling policy), and/or admission control policy (e.g.,connection admission control (CAC) policy, which dictates the adding orremoving of terminals (users)).

After the SRM 140 generates the global policy 191, the SRM 140 of theGNOC 120 and/or an SRM 150 of at least one distributed network GW 145generates configuration commands 192 for configurations for theconfigurable payload 115 of at least one network access node 105 in thenetwork access node constellation 110 based on the global policy 191.

It should be noted that in some embodiments, alternatively, anoperations manager (refer to 420 of FIG. 5) may generate XML models(refer to 520 a, 520 b, 520 c, 520 d, 520 n of FIG. 5) forconfigurations for the configurable payload 115 in accordance with thedefined global policy 191. For these embodiments, an XML-basedconfiguration data translator (refer to 510 of FIG. 5) translates theXML models 520 a, 520 b, 520 c, 520 d, 520 n into flight softwarecommands to generate the payload configuration commands 192. Thedescription of FIG. 5 discusses the details of the use of XML models 520a, 520 b, 520 c, 520 d, 520 n to generate the configuration commands192. It should be noted that the operations manager 420 and theXML-based configuration data translator 510 may be located within theGNOC 120, the RNOC 180, and/or at least one distributed network GW 145.In particular, the operations manager 420 and the XML-basedconfiguration data translator 510 may be located within the SRM 140 ofthe GNOC 120, the SRM 185 of the RNOC 180, and/or the SRM 150 of atleast one distributed network GW 145.

After the configuration commands 192 have been generated, the xOC 125 ofthe GNOC 120, the RNOC 180, and/or at least one distributed network GW145 transmits the configuration commands (CMD) 192 to at least onenetwork access node 105 to configure the payload 115 of the networkaccess node(s) 105 accordingly. After the network access node(s) 105receives the configuration commands 192, the configuration commands 192command the payload 115 of the network access node(s) 105 to configurethe payload 115 according to the configuration(s) contained within theconfiguration commands 192.

After the payload 115 of the network access node(s) 105 has configuredaccording to the configuration commands 192, the network access node(s)105 will transmit telemetry (TLM) (e.g., comprising the payload 115configuration, monitoring information, and the state of health of thenetwork access node 105) 193 to the xOC 125 of the GNOC 120, the RNOC180, and/or at least one distributed network GW 145.

Then, at least one distributed network GW 145 and/or the RNOC 180 willtransmit a summary of key performance indicators (KPIs) 194, which areobtained from at least one network access node 105 to the GNOC 120. Thesummary of KPIs 194 may comprise subscriber demand, MODEM powerprofiles, beam and carrier (beam/carrier) utilization, session blockingrates, random access channel (RACH) success rates (e.g., the successrates of the RACH procedure used to allow user terminals to discover andnegotiate access to the system), bearer success rates (e.g., the successrates of bearer requests), session setup latency (e.g., length of timeto establish a link), and/or handover success rate (e.g., the successrates for beam-to-beam, inter-network access node (e.g.,satellite-to-satellite), inter-gateways (e.g., GW-to-GW), and/orinter-network (e.g., internal-to-internal network orexternal-to-external network, also referred to as roaming) handover).

In some embodiments, optionally, the RNOC 180 will generate a regionalpolicy 195. The regional policy 195 may comprise admission control,mobility management, channel allocations, carrier allocations, bearerallocations, power management, and/or forward and/or return (FWD/RTN)scheduling (e.g., downlink/uplink scheduling for user terminals). Forthese embodiments, the RNOC 180 will transmit the regional policy 195 tothe GNOC 120, either directly or via at least one distributed network GW145.

After the GNOC 120 has received the summary of KPIs 194, the GNOC 120may revise (update) the global policy 191 according to the summary ofKPIs 194 and, if necessary, according to the regional policy 195, inorder to dynamically adapt resource allocations to changes in theaggregate subscriber demand.

After the GNOC 120 has revised the global policy 191, the operation ofthe system repeats the steps following the GNOC 120 initially generatingthe global policy 191. As such, the network of network access nodes 105is self-optimizing by using closed-loop feedback of KPIs 194 (andoptionally the regional policy 195) provided by at least one distributednetwork GW 145 and/or the RNOC 180.

FIG. 2 is a block diagram 200 showing the distributed functionalarchitecture for the disclosed system for an adaptive self-optimizingnetwork using closed-loop feedback, in accordance with at least oneembodiment of the present disclosure. In this figure, GNOC functions 210and distributed network GW functions 220 are illustrated. The GNOCfunctions 210 are functions of the GNOC 120 (refer to FIG. 1), and thedistributed network GW functions 220 are functions of at least onedistributed network GW 145 (refer to FIG. 1) and/or the RNOC 180 (referto FIG. 1). As shown in this figure, the GNOC functions 210 comprise amessage queue 205 and a non-structured query language (NoSQL) database215. In addition, the GNOC functions 210 comprise connection management225 (e.g., for establishing connections from a user terminal to anetwork access node 105 within view of the user terminal and to adistributed network GW 145 through the network access node 105), beammanagement 235 (e.g., controlling the beamformer, which is physicallylocated either within the network access node 105 or within adistributed network GW 145), and carrier management 245 (e.g.,controlling the MODEM carriers within a beam). The GNOC functions 210also comprise a connection admission control (CAC) policy 230 (e.g., anetwork configuration policy (e.g., the global policy 191) generatedbased on user demand and available resources), routing management 240(e.g., controlling the routing of the signal traffic through thenetwork), and signaling management 250 (e.g., setting up sessions forthe routing).

Also in this figure, a resource manager gateway 285 allows for the GNOC120 to communicate with a distributed network GW 145 (or the RNOC 180)via JavaScript Object Notification (JSON) and/or standard web-basedinterfaces (e.g., represented state transfer (REST), hypertext transferprotocol (HTTP), and/or websocket).

As shown in this figure, the GW functions 220 comprise payloadconfiguration (P/L CFG) 255 (e.g., for configuration of the payload),forward link control (F/L CTRL) 265 (e.g., for controlling the linkbetween the network access node 105 and the distributed network GW 145(or the RNOC 180)), MODEM control 275 (e.g., controlling the MODEM,which creates the carriers), connection admission control (CAC) 260(e.g., controlling the adding or removing of user terminals based on theCAC policy 230 (e.g., global policy 191)), mobility 270 (e.g.,controlling the handover of network access nodes as they move and/or ofuser terminals as they move), and software-defined network (SDN) control280 (e.g., the routing of signals according to the CAC policy 230).

FIGS. 3A and 3B together form a flow chart showing the method foroperation of the disclosed system for an adaptive self-optimizingnetwork using closed-loop feedback relating to FIG. 1, in accordancewith at least one embodiment of the present disclosure. At the start 310of the method, a global network operations center (GNOC) receivesoperator inputs, at step 320. Then, the GNOC generates a global policyaccording to the operator inputs, at step 330.

The GNOC and/or a distributed network gateway (GW) generateconfiguration commands for configurations for at least one of thenetwork access nodes based on the global policy, at step 340. Then, theGNOC and/or the distributed network GW transmit the configurationcommands to at least one of the network access nodes, at step 350. Atleast one of the network access nodes then transmits telemetry to theGNOC and/or the distributed network GW, at step 360.

Then, a distributed network GW transmits a summary of key performanceindicators (KPIs) to the GNOC, at step 370. Optionally, a regionalnetwork operations center (RNOC) generates a regional policy, at step380. The GNOC then revises the global policy according to the summary ofkey performance indicators and, if necessary, according to the regionalpolicy, at step 390. Then, the method repeats itself by proceeding backto step 340.

FIG. 4 is a diagram 400 showing the top level architecture for thedisclosed system for an adaptive self-optimizing network usingclosed-loop feedback, in accordance with at least one embodiment of thepresent disclosure. In this figure, a network operations center (NOC)430 is shown. The NOC 430 may be a GNOC 120 or a RNOC 180, and may beco-located within a distributed network GW. The NOC 430 is shown tocomprise an operational support system/business support system (OSS/BSS)425 and an operations manager (OM) 420. The operations manager 420comprises an application programming interface (API) handler 435, adatabase 440, a SRM policy enforcement module 445, a lifecycle servicesorchestration (LSO) manager 450, and a service and configurationregistry 455. The operations manager 420 further comprises an operatorinterface (I/F) 490 that is used to provide situational awareness to theNOC 430 and OM 420 access to operators residing within the NOC 430. Inaddition, the operations manager 420 may operate within the context of acommercial operating system, such as LINUX 460.

The NOC 430 also comprises a software-defined network (SDN) controller465, which communicates with the operations manager 420 by using astandard network management system-software-defined network controller(NMS-SDNC) application program interface (API).

Also shown in this figure are an external network 471 and internalnetworks 470 a, 470 b. It should be noted that the system may comprisemore or less than two internal networks 470 a, 470 b, and/or more thanone external network 471 as is shown in this figure. The NOC 430controls operations of the internal networks 470 a, 470 b, and theexternal network 471 is controlled by a different entity.

The external network (Domain B (Peer)) 471 is shown to comprise anetwork operating system (NOS) 480 and two routers 475 a, 475 b. Inpractice, the external network 471 domain may employ alternativearchitectures than as shown. The NOS 480 and the two routers 475 a, 475b are all in communication with each other within the external network471. Users 479 associated with the external network 471 are connected tothe external network 471 via a user-to-network interface (UNI) 486 d.

The internal network (Domain A₁) 470 a is shown to comprise a backbonecore bridge (BCB) 481, a virtual network function (VNF) 476, a networkaccess node (e.g., satellite) 105, a provider backbone bridging-trafficengineering (PBB-TE) 477, and two backbone edge bridges (BEBs) 482 a,482 b. In practice, the internal network 470 a domain may employalternative architectures than as shown. The BCB 481, VNF 476, networkaccess node 105, PBB-TE 477, and BEBs 482 a, 482 b are all incommunication with each other within the internal network 470 a.

The internal network (Domain A₂) 470 b is shown to comprise three openvirtual switches (OVSs) 483 a, 483 b, 483 c. In practice, the internalnetwork 470 b domain may employ alternative architectures than as shown.The OVSs 483 a, 483 b, 483 c are all in communication with each otherwithin the internal network 470 b. Users 478 associated with theinternal networks 470 a, 470 b are connected to the internal networks470 a, 470 b via user-to-network interfaces (UNIs) 486 a, 486 b.

The external network 471 is connected to internal network 470 a and tointernal network 470 b via external network-to-network interfaces(ENNIs) 484 a, 484 b, 484 c. Internal network 470 a is connected tointernal network 470 b via internal network-to-network interfaces(INNIs) 485 a, 485 b.

It should be noted that the external network 471 and internal networks470 a, 470 b may each comprise various different components in variousdifferent combinations than as shown in FIG. 4. In particular, theexternal network 471 and the internal networks 470 a, 470 b may eachcomprise at least one of a network access node 105, a router 475, anetwork operating system (NOS) 480, an open virtual switch (OVS) 483, abackbone edge bridge (BEB) 482, a backbone core bridge (BCB) 481, avirtual network function (VNF) 476, and/or provider backbonebridging-traffic engineering (PBB-TE) 477. The network access node 105may be a space vehicle, a high-altitude platform, an airborne vehicle, aterrestrial vehicle, or a marine vehicle. In some embodiments, the spacevehicle is a satellite, and the satellite is a geosynchronous earthorbit (GEO) satellite, a low earth orbit (LEO) satellite, a medium earthorbit (MEO) satellite, or a supersynchronous GEO satellite.

During operation of the disclosed system, the operations manager 420 ofthe NOC 430 receives a user demand from the external network 471. Theaccess requests with user demand, which specifies a desired amount ofresources (e.g., bandwidth, etc.) from the internal networks 470 a, 470b to be used by (shared with) users 479 associated with the externalnetwork 471. The operations manager 420 of the NOC 430 also receives asummary of KPIs from at least one of the internal networks 470 a, 470 b.

After the operations manager 420 of the NOC 430 receives the user demandand the summary of KPIs, the operations manager 420 of the NOC 430analyzes the user demand from the access requests and the summary ofKPIs to determine whether at least one of the internal networks 470 a,470 b has available resources that can be shared with the users 479,while maintaining enforcement of pre-existing service contracts withexisting users. When the operations manager 420 of the NOC 430determines that at least one of the internal networks 470 a, 470 b hasavailable resources, the operations manager 420 of the NOC 430 willnotify the SDN controller 465 of the NOC 430 to allow the users 479associated with the external network 471 to connect to the internalnetworks 470 a, 470 b according to the available resources. The SDNcontroller 465 of the NOC 430 will then allow a specific number of users479 to connect to the internal networks 470 a, 470 b according to theamount of available resources. Then, the users 479 that are allowed toconnect to the internal networks 470 a, 470 b will proceed to connect tothe internal networks 470 a, 470 b via UNI 486 c.

It should be noted that the SDN controller 465 of the NOC 430 controlsconnections (switching) of the ENNIs 484, the INNIs 485, and the UNIs486 of the system, in addition to intra-domain connectivity.

FIG. 5 is a diagram 500 showing further details of the operationsmanager 420 of FIG. 4, in accordance with at least one embodiment of thepresent disclosure. In this figure, the operations manager 420 is shownto comprise the database (e.g., system configuration database) 440(refer to FIG. 4) and further comprise an XML-based configuration datatranslator 510. The database 440 comprises a startup configuration (Cfg)database 515, a running configuration database 525, and a candidateconfiguration database 535. The database 440 receives policy managementinformation, network topology information, service managementinformation, and network state of health and performance information tobe stored within its databases 515, 525, 535.

During operation of the disclosed system, the operations manager 420generates XML models 520 a, 520 b, 520 c, 520 d, 520 n forconfigurations for units (e.g., switches 530 a, routers 530 b, MODEMs530 c, and other devices 530 d) for the configurable payload 115 (referto FIG. 1) according to the global policy 191 (refer to FIG. 1). Afterthe XML models 520 a, 520 b, 520 c, 520 d, 520 n have been generated,the XML-based configuration data translator 510 operates as a payloadconfigurator 540, which is a translator to translate the XML models 520a, 520 b, 520 c, 520 d, 520 n into proprietary flight software commandsto be used as the configuration commands 192 (refer to FIG. 1).

FIG. 6 is a flow chart showing the method for operation of the disclosedsystem for an adaptive self-optimizing network using closed-loopfeedback relating to FIG. 4, in accordance with at least one embodimentof the present disclosure. At the start 610 of the method, a networkoperations center (NOC) receives access requests for users subscribed toan external network, at step 620. Then, the NOC receives a summary ofkey performance indicators (KPIs) from at least one internal network, atstep 630. The NOC then determines whether at least one internal networkhas available resources by analyzing the summary of KPIs and the userdemand, at step 640. When the NOC determines that there are availableresources (while maintaining enforcement of pre-existing servicecontracts with existing users), the NOC allows at least some of theusers from the external network to connect to at last one internalnetwork to the available resources, at step 650. Then, at least some ofthe users from the external network connect to at least one internalnetwork via at least one user-to-network interface (UNI), at step 660.Then, the method ends, at step 670.

FIG. 7 is a flow chart showing the method for configuring aconfiguration for a network access node relating to FIG. 5, inaccordance with at least one embodiment of the present disclosure. Atthe start 710 of the method, XML models are generated for theconfiguration for the network access node, at step 720. Then,configuration commands are generated for the network access nodeaccording to XML models, at step 730. The configuration of the networkaccess node is then configured according to the configuration commands,at step 740. Then, the method ends, at step 750.

Although particular embodiments have been shown and described, it shouldbe understood that the above discussion is not intended to limit thescope of these embodiments. While embodiments and variations of the manyaspects of the invention have been disclosed and described herein, suchdisclosure is provided for purposes of explanation and illustrationonly. Thus, various changes and modifications may be made withoutdeparting from the scope of the claims.

Where methods described above indicate certain events occurring incertain order, those of ordinary skill in the art having the benefit ofthis disclosure would recognize that the ordering may be modified andthat such modifications are in accordance with the variations of thepresent disclosure. Additionally, parts of methods may be performedconcurrently in a parallel process when possible, as well as performedsequentially. In addition, more steps or less steps of the methods maybe performed.

Accordingly, embodiments are intended to exemplify alternatives,modifications, and equivalents that may fall within the scope of theclaims.

Although certain illustrative embodiments and methods have beendisclosed herein, it can be apparent from the foregoing disclosure tothose skilled in the art that variations and modifications of suchembodiments and methods can be made without departing from the truespirit and scope of this disclosure. Many other examples exist, eachdiffering from others in matters of detail only. Accordingly, it isintended that this disclosure be limited only to the extent required bythe appended claims and the rules and principles of applicable law.

I claim:
 1. A method for sharing network resources, the methodcomprising: receiving, by a network operations center (NOC) thatcontrols operations of at least one internal network, user demand for adesired amount of available resources from the at least one internalnetwork for users from an external network; receiving, by the NOC, keyperformance indicators from the at least one internal network;determining, by the NOC, whether the at least one internal network hasthe available resources by analyzing the key performance indicators andthe user demand; and allowing, by the NOC when the NOC determines thatthere are the available resources, at least some of the users from theexternal network to connect to the at least one internal networkaccording to the available resources.
 2. The method of claim 1, whereinthe method further comprises connecting at least some of the users fromthe external network to the at least one internal network via at leastone user-to-network interface (UNI).
 3. The method of claim 1, whereinthe external network is connected to the at least one internal networkvia at least one external network-to-network interface (ENNI).
 4. Themethod of claim 1, wherein when there are more than one of the at leastone internal network, the internal networks are connected to each othervia at least one internal network-to-network interface (INNI).
 5. Themethod of claim 1, wherein users from the at least one internal networkare connected to the at least one internal network via at least oneuser-to-network interface (UNI).
 6. The method of claim 1, wherein theexternal network and the at least one internal network each comprise atleast one of a vehicle, a router, a network operating system (NOS), anopen virtual switch (OVS), a backbone edge bridge (BEB), a backbone corebridge (BCB), a virtual network function (VNF), or provider backbonebridging-traffic engineering (PBB-TE).
 7. The method of claim 6, whereinthe vehicle is one of a space vehicle, an airborne vehicle, aterrestrial vehicle, or a marine vehicle.
 8. The method of claim 7,wherein the space vehicle is a satellite, and wherein the satellite isone of a geosynchronous earth orbit (GEO) satellite, a low earth orbit(LEO) satellite, a medium earth orbit (MEO) satellite, or a super GEOsatellite.
 9. The method of claim 1, wherein a software defined network(SDN) controller of the NOC controls connections of at least oneexternal network-to-network interface (ENNI), at least one internalnetwork-to-network interface (INNI), and at least one user-to-networkinterface (UNI).
 10. The method of claim 1, wherein the method furthercomprises controlling connections, by a software-defined network (SDN)controller in communication with the NOC, of network interfaces based onthe determining of the NOC that there are the available resources.
 11. Asystem for sharing network resources, the system comprising: an externalnetwork; at least one internal network; and a network operations center(NOC) configured to control operations of the at least one internalnetwork, to receive user demand for a desired amount of availableresources from the at least one internal network for users from theexternal network, to receive key performance indicators from the atleast one internal network, to determine whether the at least oneinternal network has the available resources by analyzing the keyperformance indicators and the user demand, and to allow, when the NOCdetermines that there are the available resources, at least some of theusers from the external network to connect to the at least one internalnetwork according to the available resources.
 12. The system of claim11, wherein at least some of the users from the external network areconnected to the at least one internal network via at least oneuser-to-network interface (UNI).
 13. The system of claim 11, wherein theexternal network is connected to the at least one internal network viaat least one external network-to-network interface (ENNI).
 14. Thesystem of claim 11, wherein when there are more than one of the at leastone internal network, the internal networks are connected to each othervia at least one internal network-to-network interface (INNI).
 15. Thesystem of claim 11, wherein users from the at least one internal networkare connected to the at least one internal network via at least oneuser-to-network interface (UNI).
 16. The system of claim 11, wherein theexternal network and the at least one internal network each comprise atleast one of a vehicle, a router, a network operating system (NOS), anopen virtual switch (OVS), a backbone edge bridge (BEB), a backbone corebridge (BCB), a virtual network function (VNF), or provider backbonebridging-traffic engineering (PBB-TE).
 17. The system of claim 16,wherein the vehicle is one of a space vehicle, an airborne vehicle, aterrestrial vehicle, or a marine vehicle.
 18. The system of claim 17,wherein the space vehicle is a satellite, and wherein the satellite isone of a geosynchronous earth orbit (GEO) satellite, a low earth orbit(LEO) satellite, a medium earth orbit (MEO) satellite, or a super GEOsatellite.
 19. The system of claim 11, wherein a software definednetwork (SDN) controller of the NOC is configured to control connectionsof at least one external network-to-network interface (ENNI), at leastone internal network-to-network interface (INNI), and at least oneuser-to-network interface (UNI).
 20. The system of claim 11, wherein thesystem further comprises a software-defined network (SDN) controller, incommunication with the NOC, configured to control connections of networkinterfaces based on the NOC determining that there are the availableresources.